Dynomotion

Group: DynoMotion Message: 9878 From: Sam Marrocco Date: 7/29/2014
Subject: Multiple threads failing to output to console
I have two programs running at the same time, each compiled/downloaded/run from the KMotion applications.  Both are simple loops that printf() to the console.

When I attempt to run both (first program 1 as thread 1, then program 2 as thread 2) the only output I ever see in the console is that of the first program run. The second (no matter the order) doesn't output to the console.

Shouldn't I see the output from both programs as they run?

--

sam marrocco | chief technical officer
ringside.cutters.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com

Group: DynoMotion Message: 9886 From: TK Date: 7/30/2014
Subject: Re: Multiple threads failing to output to console
Hi Sam,

Are they tight loops sending and buffering a large number of messages?

Regards
TK

On Jul 29, 2014, at 12:38 PM, "Sam Marrocco SMarrocco@... [DynoMotion]" <DynoMotion@yahoogroups.com> wrote:

 

I have two programs running at the same time, each compiled/downloaded/run from the KMotion applications.  Both are simple loops that printf() to the console.

When I attempt to run both (first program 1 as thread 1, then program 2 as thread 2) the only output I ever see in the console is that of the first program run. The second (no matter the order) doesn't output to the console.

Shouldn't I see the output from both programs as they run?

--

sam marrocco | chief technical officer
ringside.cutters.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com

Group: DynoMotion Message: 9889 From: Sam Marrocco Date: 7/31/2014
Subject: Re: Multiple threads failing to output to console
On 7/30/2014 8:49 PM, TK tk@... [DynoMotion] wrote:
 
Hi Sam,

Are they tight loops sending and buffering a large number of messages?




I think I see what you're suggesting....
The KFlop is running the code so fast (by comparison to the console's speed in displaying IO) that the console is literally minutes behind the hardware. Stopping the code with Halt appears to have no effect because the console is still buffering the output and can continue for minutes after the hardware has stopped running code. It also explains why multiple threads didn't appear to return anything: by the time I ran the second thread, the first has bazillions of lines already cached for return so it might be a while until I saw anything from another thread started only seconds later.

Thanks!
--

sam marrocco | chief technical officer
ringside.cutters.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com